How to change the Database Identifer

Yes, I know we are not allowed to do this.

Yes, I know every new created database has its unique database identifier.

But: my predecessor has created the second database by copying the database file tree.
Now I have two databases with identical database identifier :(
thsturm - Tue Mar 02 09:55:08 EST 2010

Re: How to change the Database Identifer
doors36677 - Wed Mar 03 07:48:21 EST 2010

Why do you perceive this as a problem?

Re: How to change the Database Identifer
PaulHutchinson - Wed Mar 03 09:30:27 EST 2010

We have a similar situation - two repositories with the same database identifier.

The only problem we have encountered is when following DOORS URLs.

Assume 2 repositories (DBX and DBY) with the same database identifier and a user who accesses both.
--> When the user has repository DBY open and follows a DOORS URL originating from an element in DBX then DOORS will follow (or try to follow) the link to an element in DBY!
--> If the user has both repositories open then there is a 50/50 chance of DOORS following the link in the correct repository!

This occurs because the link "handler" checks for an open repository with a matching database identifier (ignoring the port and server information stored in the URL). Note that if the user has neither repository open then the link is followed correctly as in this case the link "handler" has to use the port and server information stored in the URL to open the repository.

Re: How to change the Database Identifer
kbmurphy - Wed Mar 03 17:16:48 EST 2010

Here's what may work...

Create new database on new server.

Export all of duplicate server's projects and users (you may need to write a script to record access rights)

Export all users/group from duplicate server.

Import users/group from duplicate server

Import dpa files

Run scripts to restore access rights.

Not fun, and there may be more steps required. And there may be another way to do this...

Re: How to change the Database Identifer
Dirk0 - Fri Mar 12 11:46:15 EST 2010

kbmurphy - Wed Mar 03 17:16:48 EST 2010
Here's what may work...

Create new database on new server.

Export all of duplicate server's projects and users (you may need to write a script to record access rights)

Export all users/group from duplicate server.

Import users/group from duplicate server

Import dpa files

Run scripts to restore access rights.

Not fun, and there may be more steps required. And there may be another way to do this...

This is the clean way,
and the dirty is ... sorry, but this way is not for an open dicussion with end-users, because this is not simple to handle :-)

Ask IBM to modify the dbid in the file hierarchy\config.dtc for you.

dirk.